Harden startup and review publication recovery - #568
Merged
Conversation
![postil-dev[bot]](https://avatars.githubusercontent.com/in/3455612?s=60&v=4){kind=small}
morgaesis
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Postil now refuses a web release that cannot complete server instrumentation startup and keeps review publication fail-closed across transaction pooling, partial deploys, and interrupted recovery.
Release preparation records generation-scoped recovery state before darkening publication or hosted inference. Recovery adopts abandoned generations atomically, deploy and scheduled recovery share one bounded queue, and only a homogeneous verified fleet can restore capabilities. This prevents mixed fleets, stale locks, uncertain pooled clients, or a killed preparation from silently reopening merge gates.